Introduction ============ Here you will find reference information that includes the majority of known problems that exist with Worms2. Please note that you should consult the documentation provided on your Worms2 CD-ROM in the first instance. However, if all else fails and you do not find a viable solution within this section, please do not hesitate to contact us directly with your problem and we will endeavour to solve it with a minimum of fuss. IMPORTANT - Microsoft DirectX 5 =============================== Worms2 is supplied with the very latest revision of Microsoft DirectX 5 and DirectPlay 5.0a for Windows95. DirectX is basically a program interface for creating and managing graphic images and multimedia effects in games such as Worms2 and is required for the game to run correctly. If you encounter any sound or video related problems with your game then please confirm initially that you are using the very latest available drivers for your audio or display device to ensure complete compatibility. Release Updates =============== Chat Menu --------- In the manual it states that the in-game chat box can be opened by using the ` key. The game now utilises the PgDn key to open the box and the PgUp key to remove it from view. It is also possible to chat directly to other players and spectators via the 'F' keys while the chat box is in use. The chat menu also incorporates a text colour key system for the network connection status of each individual machine. Please find a list of these detailed below: BLUE This indicates that a machine connection is still being established. WHITE This indicates that a machine connection has been established. RED This indicates that a machine connection has been lost temporarily. GREY This indicates that a machine has disconnected. Time out under network play --------------------------- Worms2 incorporates a system that will time out if a network connection cannot actually be established under any given protocol. Upon initial startup Worms2 will wait 400 seconds but will disconnect automatically if a connection cannot be established. If an in-game connection is no longer viable Worms2 will time out after approximately 60 seconds. Installation Issues ------------------- Symptoms: 'Runtime error' Visual C++ prompt or black screen is displayed when attempting to play a game. Cause: Included spacing between characters included in your custom destination path directory name. This is known to cause problems with your Windows Registry setup information for Worms2 and will be fixed in later revisions. Remedy: This requires a re-install of the Worms2 software. Uninstall your existing version of Worms2 (this option is available in the Worms2 program group) and then recommence the installation procedure. Please ensure that there are no spaces within the text of your custom named destination directory. For example during the installation procedure if you previously named the directory C:\Worms 2 then change to C:\Worms2 instead. Symptoms: 'error code 112' prompt interruption during installation procedure. Cause: Possible fault on CD-ROM disk. Remedy: Check disk surface for marks, dirt or possible scratches. If you still experience problems please return the software to its place of purchase for replacement. Symptoms: 'Move data process - error code 113' prompt interruption during installation procedure. Cause: Possible conflict with some MS-DOS CD-ROM system drivers. Remedy: Select 'Run' from the Windows startbar and type 'sysedit' and press return. This will allow you to manually edit your startup files. The driver within your config.sys file should be edited so that it has a 'REM' statement at the beginning of the line call. For example DEVICEHIGH = C:\CDROM\XXXX.SYS /D:MSCD000 should be changed to REM DEVICEHIGH = C:\CDROM\XXXX.SYS /D:MSCD000. The REM statement will have to be included within the MSCDEX line in your autoexec.bat file also. You should then be able to initiate and carry out the installation procedure with no apparent problems. Symptoms: 'Move data process - error code 113' prompt interruption during installation procedure. Cause: Possibility that your system is currently utilising 16bit CD-ROM device drivers. Remedy: Use a default Windows 32bit CD-ROM device driver from within your Control Panel \ Add New Hardware section. Alternatively you could enable 32bit disk access by disabling the MS-DOS compatibility for your drive if this is present within your Control Panel \ System \ Performance section. In most cases however it is recommended that as an alternative you acquire a specific CD-ROM driver update from your software vendor. Video Issues ------------ Symptoms: 'Dibeng.dll' error prompt interruption after playing the first round of a game. Cause: Dibeng.dll governs how bitmap images are produced on your Windows desktop in unison with the GDI (Graphical Device Interface). This is more than likely to be a video incompatibility with DirectDraw. Remedy: Use default Windows SVGA driver from within your Display Properties or alternatively acquire a driver update from your software vendor that is DirectX compliant. Symptoms: CD segment loading progress screen video corruption is divided into five smaller screens resulting in multiple image.. Cause: Driver incompatibility with DirectDraw. Remedy: Use default Windows SVGA driver from within your Display Properties or alternatively acquire a driver update from your software vendor that is DirectX compliant. Symptoms: Video corruption with SiS6205 video card. Cause: Driver incompatibility with DirectDraw. Remedy: Use default Windows SVGA driver from within your Display Properties or alternatively acquire a driver update from your software vendor that is DirectX compliant. Symptoms: Video corruption with Hercules Dynamite 128 video card. Cause: Driver incompatibility with DirectDraw. Remedy: Use default Windows SVGA driver from within your Display Properties or alternatively acquire a driver update from your software vendor that is DirectX compliant. Symptoms: Full Motion Video playback in reduced screen area under Windows NT. Cause: Limitations of FMV playback under Windows NT does not allow full screen display. Sound Issues ------------ Symptoms: CD Audio can be heard but no sound effects are in fact audible. Cause: Driver incompatibility with DirectSound. Remedy: Acquire a sound driver update from your software vendor that is DirectX compliant. Network Issues -------------- IMPORTANT - Network connection with non-legitimate versions of Worms2. when playing Worms2 by any form of network connection whatsoever please make sure that you are using a legitimate copy of the game. A wide variety of connection problems may occur if a version is used other than a genuine CD of Worms2. Symptoms: Connection problems under TCP/IP protocol using AOL as your online service. Cause: Worms2 requires the 32bit version of the winsock application for network play under the TCP/IP protocol. Please note that versions previous to AOL.3.0 are 16bit only and will exhibit network game problems in this particular case. Remedy: Upgrade your existing software to the AOL3.0 revision. This is currently available for download at http://www.aol.com. General Issues -------------- Symptoms: Worms2 will not run with 128Mb System RAM or over. Cause: Worms2 will not presently run with 128Mb System RAM and is a known problem. Remedy: This problem will be amended shortly with a patched version. We apologise for any inconvenience or frustration caused. Symptoms: Cheat code will not work correctly when entered. Cause: Cheat code has been incorrectly inputted. Remedy: After entering your cheat code you MUST press the backspace key afterwards to enable it. Worms2(c) 1997 Team17 Software Limited.